Don't fail if dylib outputs aren't supported
authorAlex Crichton <alex@alexcrichton.com>
Mon, 28 Sep 2015 20:52:34 +0000 (13:52 -0700)
committerAlex Crichton <alex@alexcrichton.com>
Mon, 28 Sep 2015 20:52:34 +0000 (13:52 -0700)
commitb8c7a4c475fbfb054395fb5cc61e3a677160b544
tree308dadf086b47b23621c77106d477adca256dfb9
parentc76e9d13db3fac1f234777c462469cb2bc49ee17
Don't fail if dylib outputs aren't supported

Currently it's not possible to inform Cargo about target-specific crate types,
so generating a hard error whenever a dylib is seen for a target that can't
produce dylibs is a little heavy. This commit disables management of the output
dylib (which won't actually exists) and relies on the compiler to print a
warning in the case of a dylib output on a non-dylib target.
src/cargo/ops/cargo_rustc/context.rs